Physical uplink shared channel repetitions during handover

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may transmit, to a source base station associated with a source master cell group (MCG), a physical uplink shared channel (PUSCH) repetition in one or more slots of the source MCG during a handover of the UE from the source MCG to a target MCG. The UE may perform, to a target base station associated with the target MCG, an uplink transmission in one or more slots to the target MCG during the handover, wherein PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmission to MCG are canceled and a counting of the PUSCH repetitions is based at least in part on slots of the source MCG associated with canceled PUSCH repetitions. Numerous other aspects are described.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/219,377, filed Mar. 31, 2021, which is incorporated herein byreference in its entirety.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication and to techniques and apparatuses for physical uplinkshared channel (PUSCH) repetitions during handover.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency-division multipleaccess (FDMA) systems, orthogonal frequency-division multiple access(OFDMA) systems, single-carrier frequency-division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless network may include a number of base stations (BSs) that cansupport communication for a number of user equipment (UEs). A UE maycommunicate with a BS via the downlink and uplink. “Downlink” (or“forward link”) refers to the communication link from the BS to the UE,and “uplink” (or “reverse link”) refers to the communication link fromthe UE to the BS. As will be described in more detail herein, a BS maybe referred to as a Node B, a gNB, an access point (AP), a radio head, atransmit receive point (TRP), a New Radio (NR) BS, a 5G Node B, or thelike.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipment to communicate on a municipal, national,regional, and even global level. NR, which may also be referred to as5G, is a set of enhancements to the LTE mobile standard promulgated bythe 3GPP. NR is designed to better support mobile broadband Internetaccess by improving spectral efficiency, lowering costs, improvingservices, making use of new spectrum, and better integrating with otheropen standards using orthogonal frequency division multiplexing (OFDM)with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDMand/or SC-FDM (e.g., also known as discrete Fourier transform spreadOFDM (DFT-s-OFDM)) on the uplink (UL), as well as supportingbeamforming, multiple-input multiple-output (MIMO) antenna technology,and carrier aggregation. As the demand for mobile broadband accesscontinues to increase, further improvements in LTE, NR, and other radioaccess technologies remain useful.

SUMMARY

In some aspects, a method of wireless communication performed by a UEincludes transmitting, to a source base station associated with a sourcemaster cell group (MCG), a physical uplink shared channel (PUSCH)repetition in each of one or more slots of the source MCG during a dualactive protocol stack (DAPS)-based handover of the UE from the sourceMCG to a target MCG; and performing, to a target base station associatedwith the target MCG, an uplink transmission in one or more slots to thetarget MCG during the DAPS-based handover, wherein PUSCH repetitionsassociated with the source MCG that overlap in time with the uplinktransmission to MCG are canceled and a counting of the PUSCH repetitionsis based at least in part on slots of the source MCG associated withcanceled PUSCH repetitions.

In some aspects, a method of wireless communication performed by asource base station includes transmitting, to a UE, a configurationassociated with a quantity of PUSCH repetitions; and receiving, from theUE, a PUSCH repetition in each of one or more slots of a source MCGassociated with the source base station during a DAPS-based handover ofthe UE from the source MCG to a target MCG, wherein PUSCH repetitionsthat overlap in time with an uplink transmission to the target MCG arecanceled and a counting of the PUSCH repetitions is based at least inpart on slots of the source MCG associated with canceled PUSCHrepetitions.

In some aspects, a UE for wireless communication includes a memory andone or more processors, operatively coupled to the memory, configuredto: transmit, to a source base station associated with a source MCG, aPUSCH repetition in each of one or more slots of the source MCG during aDAPS-based handover of the UE from the source MCG to a target MCG; andperform, to a target base station associated with the target MCG, anuplink transmission in one or more slots to the target MCG during theDAPS-based handover, wherein PUSCH repetitions associated with thesource MCG that overlap in time with the uplink transmission to MCG arecanceled and a counting of the PUSCH repetitions is based at least inpart on slots of the source MCG associated with canceled PUSCHrepetitions.

In some aspects, a source base station for wireless communicationincludes a memory and one or more processors, operatively coupled to thememory, configured to: transmit, to a UE, a configuration associatedwith a quantity of PUSCH repetitions; and receive, from the UE, a PUSCHrepetition in each of one or more slots of a source MCG associated withthe source base station during a DAPS-based handover of the UE from thesource MCG to a target MCG, wherein PUSCH repetitions that overlap intime with an uplink transmission to the target MCG are canceled and acounting of the PUSCH repetitions is based at least in part on slots ofthe source MCG associated with canceled PUSCH repetitions.

In some aspects, a non-transitory computer-readable medium storing a setof instructions for wireless communication includes one or moreinstructions that, when executed by one or more processors of a UE,cause the UE to: transmit, to a source base station associated with asource MCG, a PUSCH repetition in each of one or more slots of thesource MCG during a DAPS-based handover of the UE from the source MCG toa target MCG; and perform, to a target base station associated with thetarget MCG, an uplink transmission in one or more slots to the targetMCG during the DAPS-based handover, wherein PUSCH repetitions associatedwith the source MCG that overlap in time with the uplink transmission toMCG are canceled and a counting of the PUSCH repetitions is based atleast in part on slots of the source MCG associated with canceled PUSCHrepetitions.

In some aspects, a non-transitory computer-readable medium storing a setof instructions for wireless communication includes one or moreinstructions that, when executed by one or more processors of a sourcebase station, cause the source base station to: transmit, to a UE, aconfiguration associated with a quantity of PUSCH repetitions; andreceive, from the UE, a PUSCH repetition in each of one or more slots ofa source MCG associated with the source base station during a DAPS-basedhandover of the UE from the source MCG to a target MCG, wherein PUSCHrepetitions that overlap in time with an uplink transmission to thetarget MCG are canceled and a counting of the PUSCH repetitions is basedat least in part on slots of the source MCG associated with canceledPUSCH repetitions.

In some aspects, an apparatus for wireless communication includes meansfor transmitting, to a source base station associated with a source MCG,a PUSCH repetition in each of one or more slots of the source MCG duringa DAPS-based handover of the apparatus from the source MCG to a targetMCG; and means for performing, to a target base station associated withthe target MCG, an uplink transmission in one or more slots to thetarget MCG during the DAPS-based handover, wherein PUSCH repetitionsassociated with the source MCG that overlap in time with the uplinktransmission to MCG are canceled and a counting of the PUSCH repetitionsis based at least in part on slots of the source MCG associated withcanceled PUSCH repetitions.

In some aspects, a source apparatus for wireless communication includesmeans for transmitting, to a UE, a configuration associated with aquantity of PUSCH repetitions; and means for receiving, from the UE, aPUSCH repetition in each of one or more slots of a source MCG associatedwith the source apparatus during a DAPS-based handover of the UE fromthe source MCG to a target MCG, wherein PUSCH repetitions that overlapin time with an uplink transmission to the target MCG are canceled and acounting of the PUSCH repetitions is based at least in part on slots ofthe source MCG associated with canceled PUSCH repetitions.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, and/or processing system assubstantially described herein with reference to and as illustrated bythe drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purposesof illustration and description, and not as a definition of the limitsof the claims.

While aspects are described in the present disclosure by illustration tosome examples, those skilled in the art will understand that suchaspects may be implemented in many different arrangements and scenarios.Techniques described herein may be implemented using different platformtypes, devices, systems, shapes, sizes, and/or packaging arrangements.For example, some aspects may be implemented via integrated chipembodiments or other non-module-component based devices (e.g., end-userdevices, vehicles, communication devices, computing devices, industrialequipment, retail/purchasing devices, medical devices, or artificialintelligence-enabled devices). Aspects may be implemented in chip-levelcomponents, modular components, non-modular components, non-chip-levelcomponents, device-level components, or system-level components. Devicesincorporating described aspects and features may include additionalcomponents and features for implementation and practice of claimed anddescribed aspects. For example, transmission and reception of wirelesssignals may include a number of components for analog and digitalpurposes (e.g., hardware components including antennas, RF chains, poweramplifiers, modulators, buffers, processor(s), interleavers, adders, orsummers). It is intended that aspects described herein may be practicedin a wide variety of devices, components, systems, distributedarrangements, or end-user devices of varying size, shape, andconstitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network, inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a base station incommunication with a UE in a wireless network, in accordance with thepresent disclosure.

FIG. 3 is a diagram illustrating an example of a PUSCH repetition type Acounting, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of a DAPS-based handover, inaccordance with the present disclosure.

FIG. 5 is a diagram illustrating an example of an uplink cancellation ina DAPS-based handover, in accordance with the present disclosure.

FIGS. 6-10 are diagrams illustrating examples associated with PUSCHrepetitions during handover, in accordance with the present disclosure.

FIGS. 11-12 are diagrams illustrating example processes associated withPUSCH repetitions during handover, in accordance with the presentdisclosure.

FIGS. 13-14 are block diagrams of example apparatuses for wirelesscommunication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein, one skilled in the art should appreciate that thescope of the disclosure is intended to cover any aspect of thedisclosure disclosed herein, whether implemented independently of orcombined with any other aspect of the disclosure. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, the scope of thedisclosure is intended to cover such an apparatus or method which ispracticed using other structure, functionality, or structure andfunctionality in addition to or other than the various aspects of thedisclosure set forth herein. It should be understood that any aspect ofthe disclosure disclosed herein may be embodied by one or more elementsof a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

It should be noted that while aspects may be described herein usingterminology commonly associated with a 5G or NR radio access technology(RAT), aspects of the present disclosure can be applied to other RATs,such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100,in accordance with the present disclosure. The wireless network 100 maybe or may include elements of a 5G (NR) network and/or an LTE network,among other examples. The wireless network 100 may include a number ofbase stations 110 (shown as BS 110 a, BS 110 b, BS 110 c, and BS 110 d)and other network entities. A base station (BS) is an entity thatcommunicates with user equipment (UEs) and may also be referred to as anNR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmitreceive point (TRP), or the like. Each BS may provide communicationcoverage for a particular geographic area. In 3GPP, the term “cell” canrefer to a coverage area of a BS and/or a BS subsystem serving thiscoverage area, depending on the context in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or another type of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a closed subscriber group (CSG)). A BS for a macro cell may bereferred to as a macro BS. A BS for a pico cell may be referred to as apico BS. A BS for a femto cell may be referred to as a femto BS or ahome BS. In the example shown in FIG. 1 , a BS 110 a may be a macro BSfor a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102b, and a BS 110 c may be a femto BS for a femto cell 102 c. A BS maysupport one or multiple (e.g., three) cells. The terms “eNB”, “basestation”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” maybe used interchangeably herein.

In some aspects, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of amobile BS. In some aspects, the BSs may be interconnected to one anotherand/or to one or more other BSs or network nodes (not shown) in thewireless network 100 through various types of backhaul interfaces, suchas a direct physical connection or a virtual network, using any suitabletransport network.

Wireless network 100 may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (e.g., a BS or a UE) and send a transmission of the data to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that can relay transmissions for other UEs. In the example shown inFIG. 1 , a relay BS 110 d may communicate with macro BS 110 a and a UE120 d in order to facilitate communication between BS 110 a and UE 120d. A relay BS may also be referred to as a relay station, a relay basestation, a relay, or the like.

Wireless network 100 may be a heterogeneous network that includes BSs ofdifferent types, such as macro BSs, pico BSs, femto BSs, relay BSs, orthe like. These different types of BSs may have different transmit powerlevels, different coverage areas, and different impacts on interferencein wireless network 100. For example, macro BSs may have a high transmitpower level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relayBSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to a set of BSs and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, e.g., directly or indirectly via a wireless orwireline backhaul.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wirelessnetwork 100, and each UE may be stationary or mobile. A UE may also bereferred to as an access terminal, a terminal, a mobile station, asubscriber unit, a station, or the like. A UE may be a cellular phone(e.g., a smart phone), a personal digital assistant (PDA), a wirelessmodem, a wireless communication device, a handheld device, a laptopcomputer, a cordless phone, a wireless local loop (WLL) station, atablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook,a medical device or equipment, biometric sensors/devices, wearabledevices (smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart ring, smart bracelet)), anentertainment device (e.g., a music or video device, or a satelliteradio), a vehicular component or sensor, smart meters/sensors,industrial manufacturing equipment, a global positioning system device,or any other suitable device that is configured to communicate via awireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, sensors, meters,monitors, and/or location tags, that may communicate with a basestation, another device (e.g., remote device), or some other entity. Awireless node may provide, for example, connectivity for or to a network(e.g., a wide area network such as Internet or a cellular network) via awired or wireless communication link. Some UEs may be consideredInternet-of-Things (IoT) devices, and/or may be implemented as NB-IoT(narrowband internet of things) devices. Some UEs may be considered aCustomer Premises Equipment (CPE). UE 120 may be included inside ahousing that houses components of UE 120, such as processor componentsand/or memory components. In some aspects, the processor components andthe memory components may be coupled together. For example, theprocessor components (e.g., one or more processors) and the memorycomponents (e.g., a memory) may be operatively coupled, communicativelycoupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular RAT andmay operate on one or more frequencies. A RAT may also be referred to asa radio technology, an air interface, or the like. A frequency may alsobe referred to as a carrier, a frequency channel, or the like. Eachfrequency may support a single RAT in a given geographic area in orderto avoid interference between wireless networks of different RATs. Insome cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120 a and UE 120e) may communicate directly using one or more sidelink channels (e.g.,without using a base station 110 as an intermediary to communicate withone another). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol or avehicle-to-infrastructure (V2I) protocol), and/or a mesh network. Inthis case, the UE 120 may perform scheduling operations, resourceselection operations, and/or other operations described elsewhere hereinas being performed by the base station 110.

Devices of wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided based on frequency orwavelength into various classes, bands, channels, or the like. Forexample, devices of wireless network 100 may communicate using anoperating band having a first frequency range (FR1), which may span from410 MHz to 7.125 GHz, and/or may communicate using an operating bandhaving a second frequency range (FR2), which may span from 24.25 GHz to52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred toas mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 isoften referred to as a “millimeter wave” band despite being differentfrom the extremely high frequency (EHF) band (30 GHz-300 GHz) which isidentified by the International Telecommunications Union (ITU) as a“millimeter wave” band. Thus, unless specifically stated otherwise, itshould be understood that the term “sub-6 GHz” or the like, if usedherein, may broadly represent frequencies less than 6 GHz, frequencieswithin FR1, and/or mid-band frequencies (e.g., greater than 7.125 GHz).Similarly, unless specifically stated otherwise, it should be understoodthat the term “millimeter wave” or the like, if used herein, may broadlyrepresent frequencies within the EHF band, frequencies within FR2,and/or mid-band frequencies (e.g., less than 24.25 GHz). It iscontemplated that the frequencies included in FR1 and FR2 may bemodified, and techniques described herein are applicable to thosemodified frequency ranges.

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of a base station 110 incommunication with a UE 120 in a wireless network 100, in accordancewith the present disclosure. Base station 110 may be equipped with Tantennas 234 a through 234 t, and UE 120 may be equipped with R antennas252 a through 252 r, where in general T≥1 and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCS) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (e.g., encodeand modulate) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (e.g., for semi-staticresource partitioning information (SRPI)) and control information (e.g.,CQI requests, grants, and/or upper layer signaling) and provide overheadsymbols and control symbols. Transmit processor 220 may also generatereference symbols for reference signals (e.g., a cell-specific referencesignal (CRS) or a demodulation reference signal (DMRS)) andsynchronization signals (e.g., a primary synchronization signal (PSS) ora secondary synchronization signal (SSS)). A transmit (TX)multiple-input multiple-output (MIMO) processor 230 may perform spatialprocessing (e.g., precoding) on the data symbols, the control symbols,the overhead symbols, and/or the reference symbols, if applicable, andmay provide T output symbol streams to T modulators (MODs) 232 a through232 t. Each modulator 232 may process a respective output symbol stream(e.g., for OFDM) to obtain an output sample stream. Each modulator 232may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal. Tdownlink signals from modulators 232 a through 232 t may be transmittedvia T antennas 234 a through 234 t, respectively.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 and/or other base stations and may providereceived signals to demodulators (DEMODs) 254 a through 254 r,respectively. Each demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a received signal to obtain input samples.Each demodulator 254 may further process the input samples (e.g., forOFDM) to obtain received symbols. A MIMO detector 256 may obtainreceived symbols from all R demodulators 254 a through 254 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 258 may process (e.g., demodulateand decode) the detected symbols, provide decoded data for UE 120 to adata sink 260, and provide decoded control information and systeminformation to a controller/processor 280. The term“controller/processor” may refer to one or more controllers, one or moreprocessors, or a combination thereof. A channel processor may determinea reference signal received power (RSRP) parameter, a received signalstrength indicator (RSSI) parameter, a reference signal received quality(RSRQ) parameter, and/or a channel quality indicator (CQI) parameter,among other examples. In some aspects, one or more components of UE 120may be included in a housing 284.

Network controller 130 may include communication unit 294,controller/processor 290, and memory 292. Network controller 130 mayinclude, for example, one or more devices in a core network. Networkcontroller 130 may communicate with base station 110 via communicationunit 294.

Antennas (e.g., antennas 234 a through 234 t and/or antennas 252 athrough 252 r) may include, or may be included within, one or moreantenna panels, antenna groups, sets of antenna elements, and/or antennaarrays, among other examples. An antenna panel, an antenna group, a setof antenna elements, and/or an antenna array may include one or moreantenna elements. An antenna panel, an antenna group, a set of antennaelements, and/or an antenna array may include a set of coplanar antennaelements and/or a set of non-coplanar antenna elements. An antennapanel, an antenna group, a set of antenna elements, and/or an antennaarray may include antenna elements within a single housing and/orantenna elements within multiple housings. An antenna panel, an antennagroup, a set of antenna elements, and/or an antenna array may includeone or more antenna elements coupled to one or more transmission and/orreception components, such as one or more components of FIG. 2 .

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports that include RSRP, RSSI, RSRQ, and/or CQI) fromcontroller/processor 280. Transmit processor 264 may also generatereference symbols for one or more reference signals. The symbols fromtransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by modulators 254 a through 254 r (e.g.,for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In someaspects, a modulator and a demodulator (e.g., MOD/DEMOD 254) of the UE120 may be included in a modem of the UE 120. In some aspects, the UE120 includes a transceiver. The transceiver may include any combinationof antenna(s) 252, modulators and/or demodulators 254, MIMO detector256, receive processor 258, transmit processor 264, and/or TX MIMOprocessor 266. The transceiver may be used by a processor (e.g.,controller/processor 280) and memory 282 to perform aspects of any ofthe methods described herein (for example, as described with referenceto FIGS. 6-12 ).

At base station 110, the uplink signals from UE 120 and other UEs may bereceived by antennas 234, processed by demodulators 232, detected by aMIMO detector 236 if applicable, and further processed by a receiveprocessor 238 to obtain decoded data and control information sent by UE120. Receive processor 238 may provide the decoded data to a data sink239 and the decoded control information to controller/processor 240.Base station 110 may include communication unit 244 and communicate tonetwork controller 130 via communication unit 244. Base station 110 mayinclude a scheduler 246 to schedule UEs 120 for downlink and/or uplinkcommunications. In some aspects, a modulator and a demodulator (e.g.,MOD/DEMOD 232) of the base station 110 may be included in a modem of thebase station 110. In some aspects, the base station 110 includes atransceiver. The transceiver may include any combination of antenna(s)234, modulators and/or demodulators 232, MIMO detector 236, receiveprocessor 238, transmit processor 220, and/or TX MIMO processor 230. Thetransceiver may be used by a processor (e.g., controller/processor 240)and memory 242 to perform aspects of any of the methods described herein(for example, as described with reference to FIGS. 6-12 ).

Controller/processor 240 of base station 110, controller/processor 280of UE 120, and/or any other component(s) of FIG. 2 may perform one ormore techniques associated with PUSCH repetitions during handover, asdescribed in more detail elsewhere herein. For example,controller/processor 240 of base station 110, controller/processor 280of UE 120, and/or any other component(s) of FIG. 2 may perform or directoperations of, for example, process 1100 of FIG. 11 , process 1200 ofFIG. 12 , and/or other processes as described herein. Memories 242 and282 may store data and program codes for base station 110 and UE 120,respectively. In some aspects, memory 242 and/or memory 282 may includea non-transitory computer-readable medium storing one or moreinstructions (e.g., code and/or program code) for wirelesscommunication. For example, the one or more instructions, when executed(e.g., directly, or after compiling, converting, and/or interpreting) byone or more processors of the base station 110 and/or the UE 120, maycause the one or more processors, the UE 120, and/or the base station110 to perform or direct operations of, for example, process 1100 ofFIG. 11 , process 1200 of FIG. 12 , and/or other processes as describedherein. In some aspects, executing instructions may include running theinstructions, converting the instructions, compiling the instructions,and/or interpreting the instructions, among other examples.

In some aspects, a UE (e.g., UE 120) includes means for transmitting, toa source base station associated with a source MCG, a PUSCH repetitionin each of one or more slots of the source MCG during a DAPS-basedhandover of the UE from the source MCG to a target MCG; and/or means forperforming, to a target base station associated with the target MCG, anuplink transmission in one or more slots to the target MCG during theDAPS-based handover, wherein PUSCH repetitions associated with thesource MCG that overlap in time with the uplink transmission to MCG arecanceled and a counting of the PUSCH repetitions is based at least inpart on slots of the source MCG associated with canceled PUSCHrepetitions. The means for the UE to perform operations described hereinmay include, for example, one or more of antenna 252, demodulator 254,MIMO detector 256, receive processor 258, transmit processor 264, TXMIMO processor 266, modulator 254, controller/processor 280, or memory282.

In some aspects, the UE includes means for canceling the PUSCHrepetitions associated with the source MCG that overlap in time with theuplink transmission to MCG.

In some aspects, the UE includes means for canceling the PUSCHrepetitions associated with the source MCG based at least in part on alack of UE capability for power sharing between the source MCG and thetarget MCG during the DAPS-based handover.

In some aspects, the UE includes means for canceling the PUSCHrepetitions associated with the source MCG based at least in part on aUE capability of canceling uplink transmissions during the DAPS-basedhandover.

In some aspects, the UE includes means for canceling the PUSCHrepetitions associated with the source MCG based at least in part on anintra-frequency DAPS-based handover.

In some aspects, a source base station (e.g., base station 110 a)includes means for transmitting, to a UE, a configuration associatedwith a quantity of PUSCH repetitions; and/or means for receiving, fromthe UE, a PUSCH repetition in each of one or more slots of a source MCGassociated with the source base station during a DAPS-based handover ofthe UE from the source MCG to a target MCG, wherein PUSCH repetitionsthat overlap in time with an uplink transmission to the target MCG arecanceled and a counting of the PUSCH repetitions is based at least inpart on slots of the source MCG associated with canceled PUSCHrepetitions. The means for the source base station to perform operationsdescribed herein may include, for example, one or more of transmitprocessor 220, TX MIMO processor 230, modulator 232, antenna 234,demodulator 232, MIMO detector 236, receive processor 238,controller/processor 240, memory 242, or scheduler 246.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofcontroller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

FR1 and FR2 may be associated with potential bottleneck channels. Forexample, in FR1, a potential bottleneck channel may be a PUSCH forenhanced mobile broadband (eMBB). The PUSCH for eMBB may be associatedwith frequency division duplexing (FDD) or time division duplexing (TDD)with a certain slot configuration (e.g., DDDSU, DDDSUDDSUU, orDDDDDDDSUU, where “D” represents a downlink slot, “S” represents aspecial slot, and “U” represents an uplink slot). In FR1, anotherpotential bottleneck channel may be a PUSCH for Voice over InternetProtocol (VoIP). The PUSCH for VoIP may be associated with FDD or TDDwith a certain slot configuration (e.g., DDDSU, or DDDSUDDSUU). In FR2,a potential bottleneck channel may be a PUSCH for eMBB, which may beassociated with a certain slot configuration (e.g., DDDSU or DDSU). InFR2, another potential bottleneck channel may be a PUSCH for VoIP with acertain slot configuration (e.g., DDDSU or DDSU).

For PUSCH repetition type A, a UE may repeat a transport block acrossconsecutive slots applying a same symbol allocation in each slot.However, for PUSCH repetition type A, a number of PUSCH repetitions maybe based at least in part on a quantity of available uplink/specialslots, as counting PUSCH repetitions based at least in part on theconsecutive slots may limit a number of actual PUSCH repetitions.

FIG. 3 is a diagram illustrating an example 300 of a PUSCH repetitiontype A counting, in accordance with the present disclosure.

As shown by reference number 302, in a PUSCH repetition counting for TDD(unpaired spectrum), a plurality of downlink slots, uplink slots, and/orspecial slots may be provided based at least in part on a slotconfiguration. A first PUSCH repetition may be associated with a firstslot (an uplink slot or a special slot) and have a count value of 0, anda count value for each subsequent slot (e.g., uplink slot, downlinkslot, or special slot) may be incremented by one.

In this example, the first PUSCH repetition associated with the firstslot may correspond to the count value of 0, and a second PUSCHrepetition associated with a second slot may correspond to a count valueof 5, as the first slot and the second slot may be separated bynon-uplink slots (e.g., downlink slots). Further, the first slot and thesecond slot may be associated with a same symbol allocation. Forexample, when symbols 2-10 are used in the first slot for the firstPUSCH repetition, then symbols 2-10 may also be used in the second slotfor the second PUSCH repetition.

As shown by reference number 304, in a PUSCH repetition counting for FDD(paired spectrum), a plurality of PUSCH repetitions may occur based atleast in part on a slot configuration. A first PUSCH repetition may beassociated with a first slot and have a count value of 0, and a countvalue for each subsequent slot may be incremented by one.

As shown by reference number 306, in a PUSCH repetition counting for TDD(paired spectrum), a plurality of PUSCH repetitions may occur based atleast in part on a slot configuration. A first PUSCH repetition may beassociated with a first slot and have a count value of 0. In thisexample, the count value may not increment by one for each consecutiveslot, irrespective of whether a next slot is an uplink slot, a downlinkslot, or a special slot. Rather, the count value may only be incrementedfor a subsequent uplink/special slot.

In this example, the first PUSCH repetition associated with the firstslot may correspond to the count value of 0, and a second PUSCHrepetition associated with a second slot may correspond to a count valueof 1, even though the first slot and the second slot may be separated bynon-uplink slots (e.g., downlink slots). Thus, in this example, aquantity of PUSCH repetitions may be counted on a basis of availableuplink/special slots, and the quantity of PUSCH repetitions may not becounted on a basis of consecutive slots, which may limit a number ofactual PUSCH repetitions.

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3 .

FIG. 4 is a diagram illustrating an example 400 of a DAPS-basedhandover, in accordance with the present disclosure. The DAPS-basedhandover may involve a UE, a source MCG (or source base station), atarget MCG (or target base station), and a user plane function.

The DAPS-based handover may reduce a handover interruption time byenabling the UE to simultaneously connect to both the source MCG and thetarget MCG during the DAPS-based handover. The DAPS-based handover maybe applicable to an intra-frequency handover, an intra-bandinter-frequency handover, and/or an inter-band inter-frequency handover.

As shown in FIG. 4 , in a first action, a UE may perform radio resourcemanagement (RRM) reference signal measurements, where the RRM referencesignal may be a synchronization signal block (SSB) or a channel stateinformation reference signal (CSI-RS). In a second action, an eventtrigger may occur at the UE, and in a third action, the UE may transmita measurement report to the source MCG. The measurement report mayindicate the RRM reference signal measurements. In a fourth action, thesource MCG may perform a DAPS-based handover decision based at least inpart on the measurement report. In a fifth action, the source MCG mayprepare the target MCG for the DAPS-based handover.

In a sixth action, the source MCG may transmit a radio resource control(RRC) reconfiguration message to the UE. The RRC reconfiguration messagemay indicate a handover command. In a seventh action, the UE may connectto the target MCG, and in an eighth action, the UE may transmit an RRCreconfiguration complete message to the target MCG. In a ninth action,the target MCG may perform a source MCG connection release decision, andin a tenth action, the source MCG and the target MCG may communicate ahandover connection setup complete indication. In an eleventh action,the target MCG may transmit, to the UE, an instruction to release thesource MCG, and in a twelfth action, the UE may release the source MCGbased at least in part on the indication received from the target MCG.In a thirteenth action, the UE may transmit an RRC reconfigurationcomplete message to the target MCG. In a fourteenth action, UE contextinformation may be released with the source MCG. In a fifteenth action,the UE may communicate data on the target MCG.

In this example of the DAPS-based handover, the UE may be connected toboth the source MCG and the target MCG during the handover of the UEfrom the source MCG to the target MCG. For example, between action sevenand action eleven, the UE may continue data transmissions and receptionson the source MCG, even though the UE may also be connected to thetarget MCG.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 4 .

For a DAPS-based handover that is not intra-frequency, a UE may transmiton a target cell (e.g., a target cell associated with a target MCG), andthe UE may cancel a transmission to a source cell (e.g., a source cellassociated with a source MCG). In other words, the UE may transmit onlyon the target cell and may cancel the transmission to the source cell.The UE may transmit on the target cell and cancel the transmission tothe source cell based at least in part on UE transmissions on the targetcell and the source cell being in overlapping time resources, the UE notindicating a capability for power sharing between the source MCG and thetarget MCG in the DAPS-based handover, and the UE indicates a support ofuplink transmission cancellations associated with the DAPS-basedhandover.

For a DAPS-based handover that is intra-frequency, the UE may transmiton the target cell and cancel the transmission to the source cell basedat least in part on UE transmissions on the target cell and the sourcecell being in overlapping time resources.

FIG. 5 is a diagram illustrating an example 500 of an uplinkcancellation in a DAPS-based handover, in accordance with the presentdisclosure.

As shown in FIG. 5 , a UE may be connected to a source MCG and a targetMCG during the DAPS-based handover. The UE may communicate with thesource MCG based at least in part on a first slot configuration, and theUE may communicate with the target MCG based at least in part on asecond slot configuration. In this example, the first slot configurationmay be associated with a first slot that corresponds to an uplinktransmission, a second slot that corresponds to an uplink transmission,a third slot that corresponds to a non-uplink transmission (e.g., adownlink transmission), and a fourth slot that corresponds to an uplinktransmission. The second slot configuration may be associated with afirst slot that corresponds to a non-uplink transmission, a second slotthat corresponds to an uplink transmission, a third slot thatcorresponds to an uplink transmission, and a fourth slot thatcorresponds to a non-uplink transmission. In this example, since thesecond transmission associated with both the first slot configurationand the second slot configuration are uplink transmissions, the UE maycancel the second slot with the uplink transmission with respect to thesource MCG. In other words, during the second slot associated with thefirst slot configuration and the second slot configuration, the UE mayperform the uplink transmission to the target MCG and may cancel theuplink transmission to the source MCG.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 5 .

A UE may be handed over from a source MCG to a target MCG based at leastin part on a DAPS-based handover. During the DAPS-based handover, the UEmay communicate with both a source base station associated with thesource MCG and a target base station associated with the target MCG.Regardless of whether the DAPS-based handover is an intra-frequencyDAPS-based handover, the UE may perform a transmission on the target MCGand may cancel a transmission on the source MCG based at least in parton the transmission on the source MCG overlapping in time with thetransmission on the target MCG. However, a UE behavior may not bedefined for a situation in which a PUSCH transmission with repetition onthe source MCG is canceled based at least in part on an uplinktransmission on the target MCG when DAPS-based handover is enabled forthe UE.

In various aspects of techniques and apparatuses described herein, a UEmay transmit, to a source base station associated with a source MCG, aPUSCH repetition in each of one or more slots of the source MCG during aDAPS-based handover of the UE from the source MCG to a target MCG. TheUE may perform, to a target base station associated with the target MCG,an uplink transmission in one or more slots to the target MCG during theDAPS-based handover. In some aspects, the UE may cancel PUSCHrepetitions associated with the source MCG that overlap in time with theuplink transmission to MCG. In some aspects, the UE may count the PUSCHrepetitions based at least in part on slots of the source MCG associatedwith canceled PUSCH repetitions. In some aspects, the UE may count thePUSCH repetitions based at least in part on counting the slots of thesource MCG associated with the canceled PUSCH repetitions. In someaspects, the UE may count the PUSCH repetitions based at least in parton not counting the slots of the source MCG associated with the canceledPUSCH repetitions.

FIG. 6 is a diagram illustrating an example 600 of PUSCH repetitionsduring handover, in accordance with the present disclosure. As shown inFIG. 6 , example 600 includes communication between a UE (e.g., UE 120),a source base station UE (e.g., base station 110 a), and a target basestation (e.g., base station 110 b). In some aspects, the UE, the sourcebase station, and the target base station may be included in a wirelessnetwork such as wireless network 100.

As shown by reference number 602, the UE may transmit, to the sourcebase station associated with a source MCG, a PUSCH repetition in each ofone or more slots of the source MCG. The one or more slots may be uplinkslots and/or special slots. The UE may transmit PUSCH repetitions in theone or more slots of the source MCG during a DAPS-based handover of theUE from the source MCG to a target MCG. In some aspects, the PUSCHrepetitions may be associated with a PUSCH repetition Type A, in which asame symbol allocation is applied in each of the one or more slots ofthe source MCG.

In some aspects, the UE may receive, from the source base station, aconfiguration associated with a quantity of PUSCH repetitions. The UEmay transmit, to the source base station, the PUSCH repetitions in theone or more slots of the source MCG based at least in part on theconfiguration.

In some aspects, the DAPS-based handover may be associated with anFDD-to-FDD handover. In some aspects, the DAPS-based handover may beassociated with a TDD-to-TDD handover. In some aspects, the DAPS-basedhandover may be associated with a TDD-to-FDD handover. In some aspects,the DAPS-based handover may be associated with an FDD-to-TDD handover.Further, FDD may be associated with a paired spectrum and TDD may beassociated with an unpaired spectrum.

As shown by reference number 604, the UE may perform, to the target basestation associated with the target MCG, an uplink transmission in one ormore slots to the target MCG during the DAPS-based handover. The uplinktransmission may be a physical uplink control channel (PUCCH)transmission, a PUSCH transmission, a sounding reference signal (SRS), aphysical random access channel (PRACH) transmission, or a message 3(Msg3) PUSCH transmission.

In some aspects, the UE may cancel PUSCH repetitions associated with thesource MCG that overlap in time with the uplink transmission to MCG,where the one or more slots of the target MCG may be associated with theuplink transmission from the UE. In some aspects, the UE may cancel thePUSCH repetitions associated with the source MCG based at least in parton a lack of UE capability for power sharing between the source MCG andthe target MCG during the DAPS-based handover. In some aspects, the UEmay cancel the PUSCH repetitions associated with the source MCG based atleast in part on a UE capability of canceling uplink transmissionsduring the DAPS-based handover.

In some aspects, the UE may count the PUSCH repetitions based at leastin part on slots of the source MCG associated with canceled PUSCHrepetitions. In one example, the UE may count the PUSCH repetitionsbased at least in part on counting the slots of the source MCGassociated with the canceled PUSCH repetitions. In another example, theUE may count the PUSCH repetitions based at least in part on notcounting the slots of the source MCG associated with the canceled PUSCHrepetitions.

In some aspects, the PUSCH repetitions associated with the source MCGmay fully overlap in time with the uplink transmission to MCG. In someaspects, the PUSCH repetitions associated with the source MCG maypartially overlap in time with the uplink transmission to MCG.

In some aspects, when the UE may transmit a PUSCH repetition over aquantity of N_(PUSCH) ^(repeat) slots available for PUSCH repetitiontransmissions in the source MCG, and the UE does not transmit a PUSCHrepetition in a slot included in the quantity of N_(PUSCH) ^(repeat)slots due to the slot overlapping in time with an uplink transmission tothe target MCG, the UE may or may not count the slot included in thequantity of N_(PUSCH) ^(repeat) slots. The slot in the quantity ofN_(PUSCH) ^(repeat) slots may be the slot associated with a canceledPUSCH repetition due to the slot overlapping in time with the uplinktransmission to the target MCG. In this example, N_(PUSCH) ^(repeat) mayrepresent a slot (e.g., an uplink slot or a special slot) associatedwith a PUSCH repetition. The uplink transmission to the target MCG maybe associated with a PUCCH, a PUSCH, an SRS, a PRACH, or a Msg3 PUSCH.

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 6 .

FIG. 7 is a diagram illustrating an example 700 of PUSCH repetitionsduring handover, in accordance with the present disclosure.

As shown in FIG. 7 , a plurality of slots may be configured for PUSCHrepetition transmissions to a source MCG, and a plurality of slots maybe configured for uplink transmissions (e.g., PUCCH transmissions, PUSCHtransmissions, SRS transmissions, PRACH transmissions, and/or Msg3 PUSCHtransmissions) to a target MCG. A UE may perform PUSCH repetitiontransmissions to the source MCG on one or more slots associated with thesource MCG, and the UE may perform uplink transmissions to the targetMCG on one or more slots associated with the target MCG. However, forslots associated with the source MCG that overlap in time with uplinktransmissions in slots associated with the target MCG, the UE may cancelPUSCH repetition transmissions in those slots associated with the sourceMCG. In other words, the UE may cancel the PUSCH repetitiontransmissions in those slots and instead may perform the uplinktransmissions to the target MCG.

A slot format configuration (e.g., a configuration of uplink slots,downlink slots, and special slots) may be defined for the source MCG anda slot format configuration may be defined for the target MCG. In anFDD-to-FDD handover, in a first counting scheme in which the UE countsslot(s) of the source MCG that are associated with canceled PUSCHrepetition transmissions due to uplink transmissions to the target MCGthat overlap in time resources, the UE may associate a first slot with afirst PUSCH repetition transmission with a count value of 0, and eachsubsequent slot may be associated with a count value that is incrementedby one, irrespective of whether a subsequent slot is associated with acanceled PUSCH repetition transmission. In a second counting scheme inwhich the UE does not count slot(s) of the source MCG that areassociated with canceled PUSCH repetition transmissions due to uplinktransmissions to the target MCG that overlap in time resources, the UEmay associate a first slot with a first PUSCH repetition transmissionwith a count value of 0, and each subsequent slot that is associatedwith a PUSCH repetition transmission (e.g., not a canceled PUSCHrepetition transmission) may be associated with a count value that isincremented by one.

As an example, in the second counting scheme, slots 5 and 6 may not becounted since the PUSCH repetition transmission to the source MCG iscanceled based at least in part on the uplink transmission to the targetMCG.

As indicated above, FIG. 7 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 7 .

FIG. 8 is a diagram illustrating an example 800 of PUSCH repetitionsduring handover, in accordance with the present disclosure.

As shown in FIG. 8 , a slot format configuration (e.g., a configurationof uplink slots, downlink slots, and special slots) may be defined forthe source MCG and a slot format configuration may be defined for thetarget MCG. In a TDD-to-TDD handover, in a first counting scheme inwhich the UE counts slot(s) of the source MCG that are associated withcanceled PUSCH repetition transmissions due to uplink transmissions tothe target MCG that overlap in time resources, the UE may associate afirst slot with a first PUSCH repetition transmission with a count valueof 0, and each subsequent slot may be associated with a count value thatis incremented by one, irrespective of whether a subsequent slot isassociated with a canceled PUSCH repetition transmission. In a secondcounting scheme in which the UE does not count slot(s) of the source MCGthat are associated with canceled PUSCH repetition transmissions due touplink transmissions to the target MCG that overlap in time resources,the UE may associate a first slot with a first PUSCH repetitiontransmission with a count value of 0, and each subsequent slot that isassociated with a PUSCH repetition transmission (e.g., not a canceledPUSCH repetition transmission) may be associated with a count value thatis incremented by one.

As indicated above, FIG. 8 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 8 .

FIG. 9 is a diagram illustrating an example 900 of PUSCH repetitionsduring handover, in accordance with the present disclosure.

As shown in FIG. 9 , a slot format configuration (e.g., a configurationof uplink slots, downlink slots, and special slots) may be defined forthe source MCG and a slot format configuration may be defined for thetarget MCG. In a TDD-to-TDD handover, in a first counting scheme inwhich the UE counts slot(s) of the source MCG that are associated withcanceled PUSCH repetition transmissions due to uplink transmissions tothe target MCG that overlap in time resources, the UE may associate afirst slot with a first PUSCH repetition transmission with a count valueof 0, and each subsequent slot may be associated with a count value thatis incremented by one, irrespective of whether a subsequent slot isassociated with a canceled PUSCH repetition transmission. In a secondcounting scheme in which the UE does not count slot(s) of the source MCGthat are associated with canceled PUSCH repetition transmissions due touplink transmissions to the target MCG that overlap in time resources,the UE may associate a first slot with a first PUSCH repetitiontransmission with a count value of 0, and each subsequent slot that isassociated with a PUSCH repetition transmission (e.g., not a canceledPUSCH repetition transmission) may be associated with a count value thatis incremented by one.

As indicated above, FIG. 9 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 9 .

FIG. 10 is a diagram illustrating an example 1000 of PUSCH repetitionsduring handover, in accordance with the present disclosure.

As shown in FIG. 10 , a slot format configuration (e.g., a configurationof uplink slots, downlink slots, and special slots) may be defined forthe source MCG and a slot format configuration may be defined for thetarget MCG. In a TDD-to-TDD handover, in a first counting scheme inwhich the UE counts slot(s) of the source MCG that are associated withcanceled PUSCH repetition transmissions due to uplink transmissions tothe target MCG that overlap in time resources, the UE may associate afirst slot with a first PUSCH repetition transmission with a count valueof 0, and each subsequent slot may be associated with a count value thatis incremented by one, irrespective of whether a subsequent slot isassociated with a canceled PUSCH repetition transmission. In a secondcounting scheme in which the UE does not count slot(s) of the source MCGthat are associated with canceled PUSCH repetition transmissions due touplink transmissions to the target MCG that overlap in time resources,the UE may associate a first slot with a first PUSCH repetitiontransmission with a count value of 0, and each subsequent slot that isassociated with a PUSCH repetition transmission (e.g., not a canceledPUSCH repetition transmission) may be associated with a count value thatis incremented by one.

As indicated above, FIG. 10 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 10 .

FIG. 11 is a diagram illustrating an example process 1100 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 1100 is an example where the UE (e.g., UE 120) performsoperations associated with PUSCH repetitions during handover.

As shown in FIG. 11 , in some aspects, process 1100 may includetransmitting, to a source base station associated with a source MCG, aPUSCH repetition in each of one or more slots of the source MCG during aDAPS-based handover of the UE from the source MCG to a target MCG (block1110). For example, the UE (e.g., using transmission component 1304,depicted in FIG. 13 ) may transmit, to a source base station associatedwith a source MCG, a PUSCH repetition in each of one or more slots ofthe source MCG during a DAPS-based handover of the UE from the sourceMCG to a target MCG, as described above.

As further shown in FIG. 11 , in some aspects, process 1100 may includeperforming, to a target base station associated with the target MCG, anuplink transmission in one or more slots to the target MCG during theDAPS-based handover, wherein PUSCH repetitions associated with thesource MCG that overlap in time with the uplink transmission to MCG arecanceled and a counting of the PUSCH repetitions is based at least inpart on slots of the source MCG associated with canceled PUSCHrepetitions (block 1120). For example, the UE (e.g., using transmissioncomponent 1304, depicted in FIG. 13 ) may perform, to a target basestation associated with the target MCG, an uplink transmission in one ormore slots to the target MCG during the DAPS-based handover, whereinPUSCH repetitions associated with the source MCG that overlap in timewith the uplink transmission to MCG are canceled and a counting of thePUSCH repetitions is based at least in part on slots of the source MCGassociated with canceled PUSCH repetitions, as described above.

Process 1100 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the counting of the PUSCH repetitions includescounting the slots of the source MCG associated with the canceled PUSCHrepetitions.

In a second aspect, alone or in combination with the first aspect, thecounting of the PUSCH repetitions includes not counting the slots of thesource MCG associated with the canceled PUSCH repetitions.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the PUSCH repetitions associated with the source MCGfully overlap in time with the uplink transmission to MCG.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the PUSCH repetitions associated with thesource MCG partially overlap in time with the uplink transmission toMCG.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the uplink transmission in the one or more slotsof the target MCG during the DAPS-based handover is one of a physicaluplink control channel transmission, a PUSCH transmission, a soundingreference signal, a physical random access channel transmission, or aMsg3 PUSCH transmission.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the DAPS-based handover is associated with anFDD-to-FDD handover, a TDD-to-TDD handover, a TDD-to-FDD handover, or anFDD-to-TDD handover, wherein FDD is associated with a paired spectrumand TDD is associated with an unpaired spectrum.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the PUSCH repetitions are associated with aPUSCH repetition Type A, in which a same symbol allocation is applied ineach of the one or more slots of the source MCG.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, process 1100 includes canceling the PUSCHrepetitions associated with the source MCG that overlap in time with theuplink transmission to MCG.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, process 1100 includes canceling the PUSCHrepetitions associated with the source MCG based at least in part on alack of UE capability for power sharing between the source MCG and thetarget MCG during the DAPS-based handover.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, process 1100 includes canceling the PUSCHrepetitions associated with the source MCG based at least in part on aUE capability of canceling uplink transmissions during the DAPS-basedhandover.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, process 1100 includes canceling the PUSCHrepetitions associated with the source MCG based at least in part on anintra-frequency DAPS-based handover.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the one or more slots of the source MCGinclude one or more of uplink slots or special slots; and the one ormore slots of the target MCG include one or more of uplink slots orspecial slots.

Although FIG. 11 shows example blocks of process 1100, in some aspects,process 1100 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 11 .Additionally, or alternatively, two or more of the blocks of process1100 may be performed in parallel.

FIG. 12 is a diagram illustrating an example process 1200 performed, forexample, by a source base station, in accordance with the presentdisclosure. Example process 1200 is an example where the source basestation (e.g., source base station 110) performs operations associatedwith PUSCH repetitions during handover.

As shown in FIG. 12 , in some aspects, process 1200 may includetransmitting, to a UE, a configuration associated with a quantity ofPUSCH repetitions (block 1210). For example, the source base station(e.g., using transmission component 1404, depicted in FIG. 14 ) maytransmit, to a UE, a configuration associated with a quantity of PUSCHrepetitions, as described above.

As further shown in FIG. 12 , in some aspects, process 1200 may includereceiving, from the UE, a PUSCH repetition in each of one or more slotsof a source MCG associated with the source base station during aDAPS-based handover of the UE from the source MCG to a target MCG,wherein PUSCH repetitions that overlap in time with an uplinktransmission to the target MCG are canceled and a counting of the PUSCHrepetitions is based at least in part on slots of the source MCGassociated with canceled PUSCH repetitions (block 1220). For example,the source base station (e.g., using reception component 1402, depictedin FIG. 14 ) may receive, from the UE, a PUSCH repetition in each of oneor more slots of a source MCG associated with the source base stationduring a DAPS-based handover of the UE from the source MCG to a targetMCG, wherein PUSCH repetitions that overlap in time with an uplinktransmission to the target MCG are canceled and a counting of the PUSCHrepetitions is based at least in part on slots of the source MCGassociated with canceled PUSCH repetitions, as described above.

Process 1200 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the counting of the PUSCH repetitions is based atleast in part on counting the slots of the source MCG associated withthe canceled PUSCH repetitions.

In a second aspect, alone or in combination with the first aspect, thecounting of the PUSCH repetitions is based at least in part on notcounting the slots of the source MCG associated with the canceled PUSCHrepetitions.

Although FIG. 12 shows example blocks of process 1200, in some aspects,process 1200 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 12 .Additionally, or alternatively, two or more of the blocks of process1200 may be performed in parallel.

FIG. 13 is a block diagram of an example apparatus 1300 for wirelesscommunication. The apparatus 1300 may be a UE, or a UE may include theapparatus 1300. In some aspects, the apparatus 1300 includes a receptioncomponent 1302 and a transmission component 1304, which may be incommunication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 1300 maycommunicate with another apparatus 1306 (such as a UE, a base station,or another wireless communication device) using the reception component1302 and the transmission component 1304. As further shown, theapparatus 1300 may include a cancellation component 1308, among otherexamples.

In some aspects, the apparatus 1300 may be configured to perform one ormore operations described herein in connection with FIGS. 6-10 .Additionally, or alternatively, the apparatus 1300 may be configured toperform one or more processes described herein, such as process 1100 ofFIG. 11 . In some aspects, the apparatus 1300 and/or one or morecomponents shown in FIG. 13 may include one or more components of the UEdescribed above in connection with FIG. 2 . Additionally, oralternatively, one or more components shown in FIG. 13 may beimplemented within one or more components described above in connectionwith FIG. 2 . Additionally, or alternatively, one or more components ofthe set of components may be implemented at least in part as softwarestored in a memory. For example, a component (or a portion of acomponent) may be implemented as instructions or code stored in anon-transitory computer-readable medium and executable by a controlleror a processor to perform the functions or operations of the component.

The reception component 1302 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1306. The reception component1302 may provide received communications to one or more other componentsof the apparatus 1300. In some aspects, the reception component 1302 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1306. In some aspects, the reception component 1302 may include one ormore antennas, a demodulator, a MIMO detector, a receive processor, acontroller/processor, a memory, or a combination thereof, of the UEdescribed above in connection with FIG. 2 .

The transmission component 1304 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1306. In some aspects, one or moreother components of the apparatus 1306 may generate communications andmay provide the generated communications to the transmission component1304 for transmission to the apparatus 1306. In some aspects, thetransmission component 1304 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1306. In some aspects, the transmission component 1304may include one or more antennas, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described above in connection with FIG. 2. In some aspects, the transmission component 1304 may be co-locatedwith the reception component 1302 in a transceiver.

The transmission component 1304 may transmit, to a source base stationassociated with a source MCG, a PUSCH repetition in each of one or moreslots of the source MCG during a DAPS-based handover of the UE from thesource MCG to a target MCG. The transmission component 1304 may perform,to a target base station associated with the target MCG, an uplinktransmission in one or more slots to the target MCG during theDAPS-based handover, wherein PUSCH repetitions associated with thesource MCG that overlap in time with the uplink transmission to MCG arecanceled and a counting of the PUSCH repetitions is based at least inpart on slots of the source MCG associated with canceled PUSCHrepetitions.

The cancellation component 1308 may cancel the PUSCH repetitionsassociated with the source MCG that overlap in time with the uplinktransmission to MCG. The cancellation component 1308 may cancel thePUSCH repetitions associated with the source MCG based at least in parton a lack of UE capability for power sharing between the source MCG andthe target MCG during the DAPS-based handover. The cancellationcomponent 1308 may cancel the PUSCH repetitions associated with thesource MCG based at least in part on a UE capability of canceling uplinktransmissions during the DAPS-based handover. The cancellation component1308 may cancel the PUSCH repetitions associated with the source MCGbased at least in part on an intra-frequency DAPS-based handover.

The number and arrangement of components shown in FIG. 13 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 13 . Furthermore, two or more components shownin FIG. 13 may be implemented within a single component, or a singlecomponent shown in FIG. 13 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 13 may perform one or more functions describedas being performed by another set of components shown in FIG. 13 .

FIG. 14 is a block diagram of an example apparatus 1400 for wirelesscommunication. The apparatus 1400 may be a source base station, or asource base station may include the apparatus 1400. In some aspects, theapparatus 1400 includes a reception component 1402 and a transmissioncomponent 1404, which may be in communication with one another (forexample, via one or more buses and/or one or more other components). Asshown, the apparatus 1400 may communicate with another apparatus 1406(such as a UE, a base station, or another wireless communication device)using the reception component 1402 and the transmission component 1404.

In some aspects, the apparatus 1400 may be configured to perform one ormore operations described herein in connection with FIGS. 6-10 .Additionally, or alternatively, the apparatus 1400 may be configured toperform one or more processes described herein, such as process 1200 ofFIG. 12 . In some aspects, the apparatus 1400 and/or one or morecomponents shown in FIG. 14 may include one or more components of thesource base station described above in connection with FIG. 2 .Additionally, or alternatively, one or more components shown in FIG. 14may be implemented within one or more components described above inconnection with FIG. 2 . Additionally, or alternatively, one or morecomponents of the set of components may be implemented at least in partas software stored in a memory. For example, a component (or a portionof a component) may be implemented as instructions or code stored in anon-transitory computer-readable medium and executable by a controlleror a processor to perform the functions or operations of the component.

The reception component 1402 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1406. The reception component1402 may provide received communications to one or more other componentsof the apparatus 1400. In some aspects, the reception component 1402 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1406. In some aspects, the reception component 1402 may include one ormore antennas, a demodulator, a MIMO detector, a receive processor, acontroller/processor, a memory, or a combination thereof, of the sourcebase station described above in connection with FIG. 2 .

The transmission component 1404 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1406. In some aspects, one or moreother components of the apparatus 1406 may generate communications andmay provide the generated communications to the transmission component1404 for transmission to the apparatus 1406. In some aspects, thetransmission component 1404 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1406. In some aspects, the transmission component 1404may include one or more antennas, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the source base station described above inconnection with FIG. 2 . In some aspects, the transmission component1404 may be co-located with the reception component 1402 in atransceiver.

The transmission component 1404 may transmit, to a UE, a configurationassociated with a quantity of PUSCH repetitions. The reception component1402 may receive, from the UE, a PUSCH repetition in each of one or moreslots of a source MCG associated with the source base station during aDAPS-based handover of the UE from the source MCG to a target MCG,wherein PUSCH repetitions that overlap in time with an uplinktransmission to the target MCG are canceled and a counting of the PUSCHrepetitions is based at least in part on slots of the source MCGassociated with canceled PUSCH repetitions.

The number and arrangement of components shown in FIG. 14 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 14 . Furthermore, two or more components shownin FIG. 14 may be implemented within a single component, or a singlecomponent shown in FIG. 14 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 14 may perform one or more functions describedas being performed by another set of components shown in FIG. 14 .

The following provides an overview of some Aspects of the presentdisclosure:

-   -   Aspect 1: A method of wireless communication performed by a user        equipment (UE), comprising: transmitting, to a source base        station associated with a source master cell group (MCG), a        physical uplink shared channel (PUSCH) repetition in each of one        or more slots of the source MCG during a dual active protocol        stack (DAPS)-based handover of the UE from the source MCG to a        target MCG; and performing, to a target base station associated        with the target MCG, an uplink transmission in one or more slots        to the target MCG during the DAPS-based handover, wherein PUSCH        repetitions associated with the source MCG that overlap in time        with the uplink transmission to MCG are canceled and a counting        of the PUSCH repetitions is based at least in part on slots of        the source MCG associated with canceled PUSCH repetitions.    -   Aspect 2: The method of Aspect 1, wherein the counting of the        PUSCH repetitions includes counting the slots of the source MCG        associated with the canceled PUSCH repetitions.    -   Aspect 3: The method of any of Aspects 1 through 2, wherein the        counting of the PUSCH repetitions includes not counting the        slots of the source MCG associated with the canceled PUSCH        repetitions.    -   Aspect 4: The method of any of Aspects 1 through 3, wherein the        PUSCH repetitions associated with the source MCG fully overlap        in time with the uplink transmission to MCG.    -   Aspect 5: The method of any of Aspects 1 through 4, wherein the        PUSCH repetitions associated with the source MCG partially        overlap in time with the uplink transmission to MCG.    -   Aspect 6: The method of any of Aspects 1 through 5, wherein the        uplink transmission in the one or more slots of the target MCG        during the DAPS-based handover is one of: a physical uplink        control channel transmission, a PUSCH transmission, a sounding        reference signal, a physical random access channel transmission,        or a message 3 (Msg3) PUSCH transmission.    -   Aspect 7: The method of any of Aspects 1 through 6, wherein the        DAPS-based handover is associated with a frequency division        duplexing (FDD)-to-FDD handover, a time division duplexing        (TDD)-to-TDD handover, a TDD-to-FDD handover, or an FDD-to-TDD        handover, wherein FDD is associated with a paired spectrum and        TDD is associated with an unpaired spectrum.    -   Aspect 8: The method of any of Aspects 1 through 7, wherein the        PUSCH repetitions are associated with a PUSCH repetition Type A,        in which a same symbol allocation is applied in each of the one        or more slots of the source MCG.    -   Aspect 9: The method of any of Aspects 1 through 8, further        comprising: canceling the PUSCH repetitions associated with the        source MCG that overlap in time with the uplink transmission to        MCG.    -   Aspect 10: The method of any of Aspects 1 through 9, further        comprising: canceling the PUSCH repetitions associated with the        source MCG based at least in part on a lack of UE capability for        power sharing between the source MCG and the target MCG during        the DAPS-based handover.    -   Aspect 11: The method of any of Aspects 1 through 10, further        comprising: canceling the PUSCH repetitions associated with the        source MCG based at least in part on a UE capability of        canceling uplink transmissions during the DAPS-based handover.    -   Aspect 12: The method of any of Aspects 1 through 11, further        comprising: canceling the PUSCH repetitions associated with the        source MCG based at least in part on an intra-frequency        DAPS-based handover.    -   Aspect 13: The method of any of Aspects 1 through 12, wherein:        the one or more slots of the source MCG include one or more of        uplink slots or special slots; and the one or more slots of the        target MCG include one or more of uplink slots or special slots.    -   Aspect 14: A method of wireless communication performed by a        source base station, comprising: transmitting, to a user        equipment (UE), a configuration associated with a quantity of        physical uplink shared channel (PUSCH) repetitions; and        receiving, from the UE, a PUSCH repetition in each of one or        more slots of a source master cell group (MCG) associated with        the source base station during a dual active protocol stack        (DAPS)-based handover of the UE from the source MCG to a target        MCG, wherein PUSCH repetitions that overlap in time with an        uplink transmission to the target MCG are canceled and a        counting of the PUSCH repetitions is based at least in part on        slots of the source MCG associated with canceled PUSCH        repetitions.    -   Aspect 15: The method of Aspect 14, wherein the counting of the        PUSCH repetitions is based at least in part on counting the        slots of the source MCG associated with the canceled PUSCH        repetitions.    -   Aspect 16: The method of any of Aspects 14 through 15, wherein        the counting of the PUSCH repetitions is based at least in part        on not counting the slots of the source MCG associated with the        canceled PUSCH repetitions.    -   Aspect 17: An apparatus for wireless communication at a device,        comprising a processor; memory coupled with the processor; and        instructions stored in the memory and executable by the        processor to cause the apparatus to perform the method of one or        more Aspects of Aspects 1-13.    -   Aspect 18: A device for wireless communication, comprising a        memory and one or more processors coupled to the memory, the        memory and the one or more processors configured to perform the        method of one or more Aspects of Aspects 1-13.    -   Aspect 19: An apparatus for wireless communication, comprising        at least one means for performing the method of one or more        Aspects of Aspects 1-13.    -   Aspect 20: A non-transitory computer-readable medium storing        code for wireless communication, the code comprising        instructions executable by a processor to perform the method of        one or more Aspects of Aspects 1-13.    -   Aspect 21: A non-transitory computer-readable medium storing a        set of instructions for wireless communication, the set of        instructions comprising one or more instructions that, when        executed by one or more processors of a device, cause the device        to perform the method of one or more Aspects of Aspects 1-13.    -   Aspect 22: An apparatus for wireless communication at a device,        comprising a processor; memory coupled with the processor; and        instructions stored in the memory and executable by the        processor to cause the apparatus to perform the method of one or        more Aspects of Aspects 14-16.    -   Aspect 23: A device for wireless communication, comprising a        memory and one or more processors coupled to the memory, the        memory and the one or more processors configured to perform the        method of one or more Aspects of Aspects 14-16.    -   Aspect 24: An apparatus for wireless communication, comprising        at least one means for performing the method of one or more        Aspects of Aspects 14-16.    -   Aspect 25: A non-transitory computer-readable medium storing        code for wireless communication, the code comprising        instructions executable by a processor to perform the method of        one or more Aspects of Aspects 14-16.    -   Aspect 26: A non-transitory computer-readable medium storing a        set of instructions for wireless communication, the set of        instructions comprising one or more instructions that, when        executed by one or more processors of a device, cause the device        to perform the method of one or more Aspects of Aspects 14-16.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware and/or a combination of hardware and software. “Software”shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,and/or functions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a processor is implemented in hardware and/ora combination of hardware and software. It will be apparent that systemsand/or methods described herein may be implemented in different forms ofhardware and/or a combination of hardware and software. The actualspecialized control hardware or software code used to implement thesesystems and/or methods is not limiting of the aspects. Thus, theoperation and behavior of the systems and/or methods were describedherein without reference to specific software code—it being understoodthat software and hardware can be designed to implement the systemsand/or methods based, at least in part, on the description herein.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one claim, the disclosureof various aspects includes each dependent claim in combination withevery other claim in the claim set. As used herein, a phrase referringto “at least one of” a list of items refers to any combination of thoseitems, including single members. As an example, “at least one of: a, b,or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well asany combination with multiples of the same element (e.g., a-a, a-a-a,a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or anyother ordering of a, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items (e.g.,related items, unrelated items, or a combination of related andunrelated items), and may be used interchangeably with “one or more.”Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise. Also, as used herein, the term “or”is intended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (e.g.,if used in combination with “either” or “only one of”).

1. (canceled)
 2. An apparatus for wireless communication at a userequipment (UE), comprising: one or more memories; and one or moreprocessors, coupled to the one or more memories, configured to cause theUE to: transmit, to a source cell associated with a source master cellgroup (MCG), a physical uplink shared channel (PUSCH) repetition in eachof one or more slots; and perform, during a dual active protocol stack(DAPS)-based handover of the UE from the source MCG to a target MCG, atransmission on a target cell associated with the target MCG, whereinPUSCH repetitions associated with the source cell that overlap in timewith the transmission on the target cell are canceled.
 3. The apparatusof claim 2, wherein the one or more processors are further configuredto: count the PUSCH repetitions based at least in part on counting slotsassociated with the canceled PUSCH repetitions.
 4. The apparatus ofclaim 2, wherein the PUSCH repetitions are associated with a PUSCHrepetition Type A, in which a same symbol allocation is applied in eachof the one or more slots.
 5. The apparatus of claim 2, wherein the oneor more processors are further configured to: cancel the PUSCHrepetitions to the source cell that overlap in time with thetransmission on the target cell.
 6. The apparatus of claim 2, whereinthe one or more processors are further configured to: cancel the PUSCHrepetitions associated with the source cell based at least in part onthe UE not indicating a capability for power sharing between the sourcecell and the target cell in the DAPS-based handover.
 7. The apparatus ofclaim 6, wherein the DAPS-based handover is not an intra-frequencyDAPS-based handover.
 8. The apparatus of claim 2, wherein the one ormore processors are further configured to: cancel the PUSCH repetitionsto the source cell based at least in part on the UE indicating a supportof uplink transmission cancellations associated with the DAPS-basedhandover.
 9. The apparatus of claim 8, wherein the DAPS-based handoveris not an intra-frequency DAPS-based handover.
 10. The apparatus ofclaim 2, wherein the one or more processors are further configured to:cancel the PUSCH repetitions to the source cell based at least in parton the DAPS-based handover being an intra-frequency DAPS-based handover.11. The apparatus of claim 2, wherein: the one or more slots of thesource MCG include one or more of uplink slots or special slots; and theone or more slots of the target MCG include one or more of uplink slotsor special slots.
 12. A method of wireless communication performed by auser equipment (UE), comprising: transmitting, to a source cellassociated with a source master cell group (MCG), a physical uplinkshared channel (PUSCH) repetition in each of one or more slots; andperforming, during a dual active protocol stack (DAPS)-based handover ofthe UE from the source MCG to a target MCG, a transmission on a targetcell associated with the target MCG, wherein PUSCH repetitionsassociated with the source cell that overlap in time with thetransmission to the target MCG are canceled.
 13. The method of claim 12,further comprising: counting the PUSCH repetitions based at least inpart on counting slots associated with the canceled PUSCH repetitions.14. The method of claim 12, wherein the PUSCH repetitions are associatedwith a PUSCH repetition Type A, in which a same symbol allocation isapplied in each of the one or more slots.
 15. The method of claim 12,further comprising: cancelling the PUSCH repetitions to the source cellthat overlap in time with the transmission on the target cell.
 16. Themethod of claim 12, further comprising: cancelling the PUSCH repetitionsto the source cell based at least in part on the UE not indicating acapability for power sharing between the source cell and the target cellin the DAPS-based handover.
 17. The method of claim 16, wherein theDAPS-based handover is not an intra-frequency DAPS-based handover. 18.The method of claim 12, further comprising: cancelling the PUSCHrepetitions to the source cell based at least in part on the UEindicating a support of uplink transmission cancellations associatedwith the DAPS-based handover.
 19. The method of claim 18, wherein theDAPS-based handover is not an intra-frequency DAPS-based handover. 20.The method of claim 12, further comprising: cancelling the PUSCHrepetitions to the source cell based at least in part on the DAPS-basedhandover being an intra-frequency DAPS-based handover.
 21. The method ofclaim 12, wherein: the one or more slots of the source MCG include oneor more of uplink slots or special slots; and the one or more slots ofthe target MCG include one or more of uplink slots or special slots. 22.A non-transitory computer-readable medium storing a set of instructionsfor wireless communication, the set of instructions comprising: one ormore instructions that, when executed by one or more processors of auser equipment (UE), cause the UE to: transmit, to a source cellassociated with a source master cell group (MCG), a physical uplinkshared channel (PUSCH) repetition in each of one or more slots; andperform, during a dual active protocol stack (DAPS)-based handover ofthe UE from the source MCG to a target MCG, a transmission on a targetcell associated with the target MCG, wherein PUSCH repetitionsassociated with the source cell that overlap in time with thetransmission to the target cell are canceled.
 23. The non-transitorycomputer-readable medium of claim 22, wherein the one or moreinstructions, when executed by the one or more processors, further causethe UE to: count the PUSCH repetitions based at least in part oncounting slots associated with the canceled PUSCH repetitions.
 24. Thenon-transitory computer-readable medium of claim 22, wherein the PUSCHrepetitions are associated with a PUSCH repetition Type A, in which asame symbol allocation is applied in each of the one or more slots. 25.The non-transitory computer-readable medium of claim 22, wherein the oneor more instructions, when executed by the one or more processors,further cause the UE to: cancel the PUSCH repetitions to the source cellthat overlap in time with the transmission on the target cell.
 26. Thenon-transitory computer-readable medium of claim 22, wherein the one ormore instructions, when executed by the one or more processors, furthercause the UE to: cancel the PUSCH repetitions to the source cell basedat least in part on the UE not indicating a capability for power sharingbetween the source cell and the target cell in the DAPS-based handover.27. The non-transitory computer-readable medium of claim 26, wherein theDAPS-based handover is not an intra-frequency DAPS-based handover. 28.The non-transitory computer-readable medium of claim 22, wherein the oneor more instructions, when executed by the one or more processors,further cause the UE to: cancel the PUSCH repetitions to the source cellbased at least in part on the UE indicating a support of uplinktransmission cancellations associated with the DAPS-based handover. 29.The non-transitory computer-readable medium of claim 28, wherein theDAPS-based handover is not an intra-frequency DAPS-based handover. 30.The non-transitory computer-readable medium of claim 22, wherein the oneor more instructions, when executed by the one or more processors,further cause the UE to: cancel the PUSCH repetitions to the source cellbased at least in part on the DAPS-based handover being anintra-frequency DAPS-based handover.
 31. An apparatus for wirelesscommunication, comprising: means for transmitting, to a source cellassociated with a source master cell group (MCG), a physical uplinkshared channel (PUSCH) repetition in each of one or more slots; andmeans for performing, during a dual active protocol stack (DAPS)-basedhandover of the apparatus from the source MCG to a target MCG, atransmission on a target cell associated with the target MCG, whereinPUSCH repetitions associated with the source cell that overlap in timewith the transmission to the target cell are canceled.